Release 10.1A: OpenEdge Development:
Messaging and ESB

Exchanging messages

The following steps are necessary to allow the exchange of messages between the 4GL and JMS:

The programmer writes a 4GL program that connects to the SonicMQ Broker through the OpenEdge Adapter for SonicMQ by creating a persistent Session object procedure using OpenEdge-Install-Directory/jms/jmssession.r, OpenEdge-Install-Directory/jms/ptpsession.r, OpenEdge-Install-Directory/jms/pubsubsession.r, or
The programmer uses the 4GL-JMS API implemented by the Session objects to send and receive JMS messages through the 4GL client application.
Note: The programmer does not have to write any Java or 4GL code on the server side. That code is supplied by Progress Software Corporation and installed with the OpenEdge Adapter for SonicMQ and in the 10.1A client.